-
Notifications
You must be signed in to change notification settings - Fork 582
Updated index.md to reflect changes in GEP-2162 #3898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hi @bexxmodd. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cc @LiorLieberman |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bexxmodd.
I am missing the following:
- Mesh story in all of it and future plans for mesh
- Guidance regarding what features should be published under supportedFeatures in gateway class (only gateway features - option 1 from #3885 (comment))
- Implications for implementations that does not implement supportedFeatures (they will not be compliant)
- Transition period for everyone to start implement before we implement the logic to block the reports
/cc @mlavacca @mikemorris |
Co-authored-by: Lior Lieberman <[email protected]>
@LiorLieberman added info for all four bullet points you mentioned. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks @bexxmodd
Co-authored-by: Rob Scott <[email protected]>
Co-authored-by: Rob Scott <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bexxmodd can you update the GEP based on what landed in the other PR?
Also can you fix the release-notes?
you should have a block like this in your pr description
NONE
@LiorLieberman added information about test suite throwing an error if mesh features are published under GWC. That was the only changed in the merged PR that was not covered in this GEP update. Updated release-note in the PR description. |
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bexxmodd
Co-authored-by: Lior Lieberman <[email protected]>
Co-authored-by: Lior Lieberman <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bexxmodd!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bexxmodd, LiorLieberman, robscott The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Co-authored-by: Rob Scott <[email protected]>
Co-authored-by: Rob Scott <[email protected]>
/lgtm |
/unhold |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Does this PR introduce a user-facing change?: